Ham Radio 2000

home *** CD-ROM | disk | FTP | other *** search

/ Ham Radio 2000 / Ham Radio 2000.iso / ham2000 / antenna / azproj10 / az_ini.ps < prev next >

Wrap

Text File | 1995-07-19 | 33KB | 886 lines

%%!PS-Adobe-1.0 %!-------------------------------------- %%Title: az_ini.ps Ver 1.0 %%CreationDate: 18 Jul 95 %AZ_INI.PS v1.0 % % Is Joe's file az_ini.ps % %-------------------------------------- % AZ_INI.PS (C) 1994 Joseph Mack NA3T and Michael Katzmann NV3Z/VK2BEA/G4NYV % % AZ_INI.PS is free software; you can redistribute it and/or modify % it under the terms of the GNU General Public License as published by % the Free Software Foundation; either version 2, or (at your option) % any later version. % % This program is distributed in the hope that it will be useful, % but WITHOUT ANY WARRANTY; without even the implied warranty of % MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the % GNU General Public License for more details. % % You should have received a copy of the GNU General Public License % along with az_ini.ps; see the file COPYING. If not, write to % the Free Software Foundation, 675 Mass Ave, Cambridge, MA 02139, USA. % %-------------------------------------- % az_ini.PS - Initialisation file for AZ_PROJ.PS % % Most of the variables that are customisable in the program are here. % Unless a variable depends on a previously defined variable the % order of listing of these variables can be changed to suit yourself. % Once you get the idea of how to use this file, you can remove comments % etc, to make a smaller (easier to edit) working file. % % Other variables, which require execution of code to determine the % value of "atom" (1/2000 of page width), are in az_proj.ps. % These variable can also be changed as you wish. %-------------------------------------- % Dictionaries in Level 1 Postscript devices cannot grow (as they can in % level 2) on demand. 'userdict' will therefore run out of space, so % we define our own local dictionary. % % DO NOT MOVE THESE NEXT TWO DECLARATIONS UNLESS YOU KNOW WHAT YOU ARE DOING /az_dict 400 dict def az_dict begin %-------------------------------------- /on true def /off false def %-------------------------------------- % Options - this first section is for stuff you'll change a lot % Customising AZ_PROJ % % There are two methods "automatic" and "manual" % You choose the method with /use_automatic_option below. % % Just about every variable you want to change is in the "manual" section % of this file. (The rest, that you probably won't want to change, are % in the routines in az_proj.ps.) % In the "manual" section, the variables are grouped according % to function (eg all QTH variables are together). and these % variables are loaded as they are read in % (by the printer or by ghostscript). % % As well an "option" array immediately below contains a subset of the % variables that we think will be the most often changed. % % The program will read in both (manual and option) sets of data and if % variable /use_automatic_option is "on", the main routines in % az_proj.ps will overwrite the values previously declared in % the "manual" section. % % If you want to use this "option" array to enter things like QTH, % then make /use_automatic_option "on". % If you want to manually enter values then make /use_automatic_option "off" % and go find the variable lat_QTH and change it. % /use_automatic_option on def %on initiallise from "options" array %off initiallise from "manual" section % % For a quick start try guessing the changes to be made % in this array. If you get stuck more hints are below. % The tabbing format and grouping of variables % one or two to a line is only for your convenience. % After removing the comments at the end of the line, % you can reformat this array to 1,2,3..n variables per line. /options [ 41.6 -72.7 (ARRL HQ) % lat, lon, string, for QTH 45.0 -90.0 on % lat, lon (middle of NA), center_offset (here off, using QTH as center) 250 on % scale, using km/cm (off = degrees), off % landscape (off = portrait, on = landscape) on off % letter grid squares, labels off off % number grid squares, labels on on % compass circumference, compass radial spokes on % outer border on % DXCC countries by callsign (off = by country name) ] def %-------------------------------------- %Colors % need to set these up before we initialise colors of map objects % You can print maps on B&W printers just fine. % Postscript will print each color as some particular grey or other. % If you want lots of information in a B&W format, you will probably have % to print several different maps, since B&W with a lot of different % features will be cluttered. %Colors - starter kit, make your own % RGB values /white { 1.0 1.0 1.0 } def % white /blue { 0.0 0.0 1.0 } def % blue /darkblue { 0.0 0.0 0.5 } def % blue /green { 0.0 1.0 0.0 } def % green /darkgreen { 0.0 0.4 0.0 } def % green /cyan { 0.0 1.0 1.0 } def % cyan /red { 1.0 0.0 0.0 } def % red /magenta { 0.5 0.0 1.0 } def % magenta /brown { 0.67 0.33 0.0 } def % brown /white { 1.0 1.0 1.0 } def % white /lightgray { 0.9 0.9 0.9 } def % lightgray /gray { 0.5 0.5 0.5 } def % gray /darkgray { 0.3 0.3 0.3 } def % darkgray /lightblue { 0.33 0.33 1.0 } def % lightblue /verylightblue { 0.75 0.75 1.0 } def % lightblue /lightgreen { 0.33 1.0 0.33 } def % lightgreen /lightcyan { 0.33 1.0 1.0 } def % lightcyan /lightred { 1.0 0.33 0.33 } def % lightred /lightmagenta { 1.0 0.33 1.0 } def % lightmagenta /yellow { 1.0 1.0 0.0 } def % yellow /purple { 1.0 0.0 1.0 } def % purple /black { 0.0 0.0 0.0 } def %-------------------------------------- % Manual method (turn use_automatic_option "off" or the values controlled % by the "options" array will be overwritten) %-------------------------------------- %Title % The title will appear across top of page. /Title ( ) def % needs to be initialised, don't delete this % Example titles, comment these out if not needed. %/Title (North America) def %This title might appear on a map with 200 km/cm as the scale %/Title (Jan '95 VHF/UHF Contest - 6m log) def %This title might appear on a map with 100 km/cm as the scale %/Title (Jan '95 VHF/UHF Contest - 432 log) def %This title might appear on a map with 2000 km/cm as the scale %/Title (DXCC countries, 80m CW, 31 Dec 94) def %-------------------------------------- %QTH % Lat/long are in decimal degrees (not deg/min/sec) % lat: +ve is north, -ve is south % lon: +ve is east , -ve is west % /lat_QTH 41.6 def %(real or int) /lon_QTH -72.7 def %(real or int) /QTH_name (ARRL HQ) def %(string, parentheses are required) % To change the QTH, try one of these triplets (or your own QTH) %/lat_QTH 0 def /lon_QTH 25 def /QTH_name (Africa) def %/lat_QTH 0.1 def /lon_QTH 0.0 def /QTH_name (Equator) def %/lat_QTH -55 def /lon_QTH 160 def /QTH_name (Macquarie Is.) def %/lat_QTH -20 def /lon_QTH 120 def /QTH_name (Mid Oceania) def %/lat_QTH 89.1 def /lon_QTH 0.1 def /QTH_name (North Pole) def %/lat_QTH -89.9 def /lon_QTH 0.0 def /QTH_name (South Pole) def %/lat_QTH -34 def /lon_QTH 151 def /QTH_name (Sydney) def %/lat_QTH 36 def /lon_QTH 140 def /QTH_name (Tokyo) def %/lat_QTH 59 def /lon_QTH 18 def /QTH_name (Stockholm) def %/lat_QTH -34 def /lon_QTH 18 def /QTH_name (Capetown) def %/lat_QTH -22.86 def /lon_QTH -44.8 def /QTH_name (Rio) def %/lat_QTH 48.0 def /lon_QTH -124.0 def /QTH_name (Vancouver) def %/lat_QTH 22.0 def /lon_QTH -82.0 def /QTH_name (Havana) def %/lat_QTH 8.0 def /lon_QTH -80.0 def /QTH_name (Panama) def %/lat_QTH -27.0 def /lon_QTH -108.0 def /QTH_name (Easter Is.) def %/lat_QTH -25.0 def /lon_QTH -130.0 def /QTH_name (Pitcairn Is.) def %/lat_QTH -35.0 def /lon_QTH -160.0 def /QTH_name (Antipodes of Mediterranian) def % interesting view of Europe %/lat_QTH 52 def /lon_QTH 0 def /QTH_name (London) def %/lat_QTH 35 def /lon_QTH -90 def /QTH_name (Memphis) def %/lat_QTH 41.6 def /lon_QTH -72.7 def /QTH_name (ARRL HQ) def %/lat_QTH 38.92 def /lon_QTH -77.05 def /QTH_name (Washington DC) def %/lat_QTH 38.98847 def /lon_QTH -76.58033 def /QTH_name (NV3Z Annapolis, FM18rx) def %/lat_QTH 39.42933 def /lon_QTH -77.42536 def /QTH_name (NA3T/N3REQ Frederick, FM19) def %/lat_QTH 40.0 def /lon_QTH 60.0 def /QTH_name (Somewhere in Russia) def %/lat_QTH 52 def /lon_QTH 95 def /QTH_name (Kyzyl) def %-------------------------------------- % Center Offset: % % When the center of the map isn't your QTH, the azimuthal projection % is still made from your QTH, but the map is translated on the page. % This feature is used if you live on the edge of a continent and want % the center of the map in the center of the continent. % Or else or if you want a map of Europe as it looks from your QTH in USA, % but you only want Europe on the map. % % center_offset should be off if using nmea.dat. % The problem comes about because it's hard to change the center % of the map half way through after reading the nmea.dat file. % (it's hard enough to even change the QTH ;-( ). % Results are unpredictable if center_offset is on. /center_offset off def % on: use following lat/lon for center of map %off: use QTH for center of map. %example offset position - middle of North America /lat_center 40.0 def %(real or int) /lon_center -90.0 def %(real or int) % To change center of map try one of these % % 40 -90 true % centred on middle of N.A % 59 18 true % centred on Stockholm % -34 151 true % centred on Sydney % -24 133 true % centred on Alice Springs (Middle of Oz) % 47 7 true % centred on Berne % -10 155 true % centred on Guadalcanal %-------------------------------------- %Scale % % mapping scale is the scale you see on the bottom of a real map, % eg 1cm:100km, or 1cm:15 deg (angle subtended at earth's centre by % a line along earth's surface). The distance from the equator to pole % is 10,000km (thanks to Napoleon Bonaparte) or 90 deg. % The radius of the map, on an 'A' size or A4 page, is about 10cm. Hence - % For whole world use 2000 kms/cm % For whole world on half a page use 4000 kms/cm % For continent use 400 kms/cm % 200 kms/cm will fit 2 grid squares across at the equator % For general VHF/UHF DX use 50 kms/cm % % The alternative scaling is in degrees of solid angle between points, % subtended at earth's centre as a scale. The earth is 180 degrees % from center to edge (circumference). /scale_type on def %on : use map_scale_deg as km/cm %off: use map_scale_deg as deg/cm /map_scale_deg 200 def %(real or int) %-------------------------------------- %Orientation /landscape off def %on : landscape %off: portrait %-------------------------------------- %Grid squares and labelling % These allow drawing of grid square borders % and labelling of grid squares with their grid locators. % If labels are "on" the grid locator label will be put in % the middle of the grid square % Letter squares are 20x10 deg (eg FM) % Number squares are 2x1 deg (19 of FM19) % If squares are on, the border of the squares will be drawn. /draw_letter_square_borders off def %(on/off) /draw_letter_square_labels off def %(on/off) /draw_number_square_borders off def %(on/off) /draw_number_square_labels off def %(on/off) %Labelling pattern /label_all_number_squares_in_a_letter_square off def % determines labelling pattern of number_squares % on/true - label all number_squares % off/false - label number squares only on the border %(ie outer edge) of a letter square %(setting to "off" gives less clutter) /number_square_edges_dashed on def % drawing pattern for edges of number squares % on/true - dashed, off/false - continuous line % (on makes number squares less dominant than letter squares - as they should) % number of letter grid-squares north, south, east & west % of your own letter square that will be filled with number_squares % Example: % if you live in grid locator FM, % and if the values below are 1,1,0,1 % then FN (grid square to north), FL (south), and EM (west) % will have number squares drawn on them, but GM (east) will not. /grid_locator_number_squares_northern_limit 1 def /grid_locator_number_squares_southern_limit 1 def /grid_locator_number_squares_eastern_limit 0 def /grid_locator_number_squares_western_limit 1 def % Note: If all are 0, only your own local letter grid square will be filled. % to turn off ALL number squares (including your own) % set "/draw_number_square_borders" to off % %bug fix: if QTH is exactly on a letter_square edge (say on 60.000 deg E meridian) % then the routine as originally written will produce no grid squares % to E or W of the QTH. In this case I've forced the routine to produce % number squares on both sides. To save yourself this harrowing complication, % you could always put in a lat/lon like (0.001, -0.002), instead of (0,0). % There are also occasional problems with QTH's on number grid square % boundaries (eg 38N). Until that's fixed, use 38.01 say. /grid_locator_letter_color /lightred cvx def /grid_locator_number_color /lightblue cvx def %Note these colors determine both the color of the labels and the grid lines /shade 1.0 def % reduce luminance of (ie darken) grid boundaries % 1.0 - same color as grid labels % 0.66 - darker % 0.0 - black % factor for increased thickness of the equator and the UTC lines % 1 for no emphasis /grid_line_emphasis 4 def %-------------------------------------- % lines other than 10,20 deg lines for grid locators % if for instance you want every 15 deg for time zones % I have coded this to turn off if the grid_locator letters are on % so that you won't have labels corresponding to a different spacing /draw_alternate_lat_lon_spacing off def %on - use numbers below %off - use grid_locator spacing /alternate_lat_spacing 15 def /alternate_lon_spacing 15 def %15 deg = 1hr %-------------------------------------- /draw_greyline on def % day/night border, ie terminator %I know the sun is red, but everything else is red or blue /greyline_color /green cvx def % the greyline info will be derived first from sun_lat, sun_lon % if the date/time is also defined (ie not commented) then % the sun_lat, sun_lon will be calculated from them, % overwritting the values from sun_lat, sun_lon % % date/time can be read in from the nmea.dat file generated from your % gps receiver. The gps data will overwrite the date/time info entered here. % % ie priorities for calculating sun_lat, sun_lon % 1. gps info from NMEA.DAT file % if not found then % 2. date/time entered here % if not found then % sun_lat, sun_lon entered here. % date and time (UTC/Zulu) 03 /month exch def % (1..12) 22 /day exch def % (1..31) 6 /hour exch def % (0..23) 00 /min exch def % (0..59) % lat_QTH /sun_lat exch def % lon_QTH /sun_lon exch def -16.5364 /sun_lat exch def %(-23.5..23.5) 165.0 /sun_lon exch def %(-180..180) %-------------------------------------- %Compass: % to establish direction from your QTH, a compass is % centered on your QTH (even if QTH is center offset) /draw_compass_circumference on def %(on/off) draw compass circumference %if draw_compass_circumference is off and draw_compass_spokes in on % then the spokes will go to the antipodes (see below) /draw_compass_spokes on def %(on/off) draw compass spokes /compass_spoke_interval 15 def %(int, degrees between spokes) /compass_label_increment 15 def %(int, degrees between labels) % the spacing of major radial compass spokes (lines) is 30 deg % (see comment in routine "\draw_spokes") and are drawn right onto the QTH. % the spacing of minor radial compass spokes (lines) is given by % compass_spoke_interval. Suggested values are 10,15 or 45. % These minor lines do not go to the center of the compass % (ie the QTH) so as not to obliterate the QTH. /compass_spokes_to_antipodes off def % on/true - spokes go beyond compass rose to the edge of the world % off/false - compass spokes go only to circumference of compass % Note: if compass rose is not drawn, but the spokes are, then % spokes go out to antipodes no matter what value is entered here. %Compass circumference % The radius of the compass is changed automatically in multiples of % 1,2,5, to make nice round numbers for scaling. If your QTH is not % at the center of the page, part of the circumference of the compass % will/may go off the page. You can fiddle with the code in % draw_bearing_rose to make the radius smaller. Here is a fiddle % I've used. Change the number to suit you. The number "0.75" % here will fit the largest compass that sits inside 3/4 of % the page rather than the largest compass that sits % inside the whole page. This allows you some latitude to move % the center of the page away from the QTH and still have compass % contained within the page. %/compass_coerce {0.75 mul} def % reduce compass circle size /compass_coerce {} def % the normal size % pick one by commenting out the other /compass_color /yellow cvx def % yellow looks OK in daylight, % but vanishes under incandescent light /compass_label_color /black cvx def %labels for directions (30, 60, 90... etc) %-------------------------------------- /draw_outer_border on def % (on/off) border at the antipodes % on is useful for maps of the whole world % for maps of a smaller area, the border is % still calculated but it is off the edge of the map % (ie you can leave it on all the time if you like) /outer_border_color /black cvx def %-------------------------------------- /DXCC_callsigns on def % on: dxcc countries displayed as callsign %off: dxcc countries displayed as country name /circle_dxcc off def % on: print calls long concentric circles about QTH %off: print calls along horizontal straight lines /dxcc_color /black cvx def /dxcc_special_color /green cvx def /dxcc_special_color_2 /red cvx def /dxcc_bands_plotted % Frequency mask for selecting dxcc countries to be displayed. % If you want to display only the dxcc countries that you've % worked on 80m CW, then uncomment 80 in the array below and CW in the % array below that. If you want to display countries that have been worked % on 80 and and the countries that have been worked on 40m, % then remove the "%" infront of both 80 and 40. % Leave all other numbers with a "%" as the first character in the line. % % You can add frequencies and modes. Eg if we get back the bands above 200m, % say 320m, and can do spark mode on it again, then % add 320 to the band options below % and (SPARK) to the mode options below. % When you make a SPARK contact on 320m with a % country add 320 SPARK to the dxcc.dat file. % % You can use numbers in any way you want here, just as long as it's % consistent with the use and numbering in the dxcc.dat files. % A "10" in the following array will flag all of the entries in % the dxcc.dat file with "(10 xxx)" in them. % What the 10 means is up to you - it can be 10GHz, 10m or 10MHz. % % This array can have any number of integer elements (including none). % Only one element allowed per line, lines in any order. % Add, remove or comment (put "%" in front of number) out elements to suit. [ %160 %80 %75 40 %30 %20 %15 %12 %10 %6 %2 ] def /dxcc_modes_plotted % Mode mask for selecting dxcc countries to be displayed. % % If you want to display only the dxcc countries that you've % worked on 80m CW, then uncomment CW in the array below, and 80 in the % array above. If you want to display countries that have been worked on % CW and the countries that have been worked on SSB, % then remove the "%" infront of both CW and SSB. % Leave all other numbers with a "%" as the first character in the line. % Note the spelling is case sensitive. % % The mode result is AND'ed with the band result. % ie if you ask for 80 CW you will get only those % countries that you've worked on 80 CW. % If you want to list all countries that you've worked on 80 or on CW, % then you'll either have to fiddle a bit or write the code yourself % (and send it to us as well). % If you want the countries that you've worked on CW, on any band, % then you'll have to uncomment all the band entries in the % dxcc_bands_plotted array above. % % This array can have any number of elements (including none). % Only one element allowed per line, lines in any order. % Add, remove or comment (have "%" in front of number) out elements to suit. [ (CW) %(SSB) %(AM) %(FM) %(SWL) %(RTTY) %(SSTV) %(packet) %(EME) %(aurora) %(MS) %(Es) %(you can add any string you like to match the corresponding string in the dxcc.dat file, even a string as long as this, as long as you reproduce it exactly in the dxcc.dat file) ] def %-------------------------------------- %Geographical Features and Drawing States within countries % Some maps are cluttered by unnecessary info. % E.g. When doing a whole world map centered on North America, % the US states and Canadian Provinces produce a lot of clutter % here you can turn selected things on or off % /state_borders_dashed on def % on: state borders are 1-3 pattern of dashes % (see Postscript book for explanation) % off: states borders are straight lines % (and they look like country borders) /draw_coast_lines on def % you can turn off the coast lines /draw_country_borders on def % and all these things here /draw_canadian_provinces on def /draw_us_states on def /draw_islands on def /draw_lakes on def % suggested by beta tester Brian Derx /draw_rivers on def /draw_australian_states on def %-------------------------------------- % Drawing circles around QTH at defined distances % Turning this on, turns off the default compass circumference % (you can still have the spokes from the compass to give direction) /distance_circles off def % % /distances_plotted %( in km) % Possible distances might be - % 1100km for E layer scattering (aurora, Es, FAI) % 900km for good 2m conditions on a contest % 700km for good 432 conditions on a contest % Maybe you just want a bull's eye drawn around your QTH at 200 km intervals % This array can have any number of integer elements (including none). % Only one element allowed per line % Add, remove or comment (have "%" in front of number) out elements to suit. % Circles are drawn in the order listed in the array. % The last distance circle in this array will have compass bearings % and labels drawn on it (so make it the circle of largest radius) [ 100 200 %300 400 %500 600 %700 800 %900 %1000 %1100 %1200 ] def %-------------------------------------- %Beacons /beacon_font /Helvetica def /beacon_font_color /black cvx def /beacon_color {beacon_font_color} def % color for standard beacons %Try (ie uncomment) this scheme when using special_beacons on color printers /beacon_special {beacon_special_2} def % special beacons are drawn in the color beacon_special_color /beacon_special_color /red cvx def %Try (ie uncomment) this scheme when using special_beacons on B/W printers %/beacon_special {beacon_special_1} def % special beacons are drawn in the center of cross hairs %/beacon_special_color {beacon_font_color} def /beacons_plotted % Beacons are turned on and off by the MHz in the frequency of the beacon % in beacon.dat. If the numbers "144" and "1296" are in this array, % then all beacons of freq 144.xxx and 1296.xxx will be plotted. % This array can have any number of integer elements (including none). % Only one element allowed per line, lines in any order. % Add, remove or comment (put "%" in front of number) out elements to suit. [ 50 51 52 %70 %71 144 %222 %432 %902 %903 %926 %1295 %1296 %2304 %2312 %3456 %5759 %5760 %10248 %10256 %10265 %10368 %24192 ] def %-------------------------------------- /grid_bands_plotted % grids worked are plotted according to the MHz in the frequency in % the file grid.dat. If the numbers "144" and "1296" are in the % array grid_bands_plotted, then all grids worked of freq 144MHz % and 1296MHz will be plotted (colored/shaded). % This array can have any number of integer elements (including none). % Only one element allowed per line, lines in any order. % Add, remove or comment (have "%" in front of number) out elements to suit. [ %50 %70 %72 144 %145 %146 %147 %222 432 %435 %902 %903 %926 %1295 1296 %2304 %2312 %3456 %5759 %5760 %10248 %10256 %10265 %10368 %24192 ] def %-------------------------------------- %Repeaters %/repeater false def % need to define this /repeater_font /Helvetica def /repeater_font_color /black cvx def /repeater_color /black cvx def %color for repeater symbol %Try (ie uncomment) this scheme when using repeater_special on color printers /repeater_special {repeater_special_2} def % special repeaters are drawn in the color repeater_special_color /repeater_special_color /red cvx def %Try (ie uncomment) this scheme when using special_repeaters on B/W printers %/repeater_special {repeater_special_1} def % special repeaters are drawn in the center of cross hairs %/repeater_special_color {repeater_font_color} def /repeaters_plotted % repeaters are plotted according to the MHz in the frequency in the % repeater.dat file. % If the numbers "147" and "441" are in the array repeaters_plotted, then % all repeater of (transmitting) freq 147.xxxMHz and 441.xxxMHz will be marked. % This array can have any number of integer elements (including none). % Only one element allowed per line, lines in any order. % Add, remove or comment (put "%" in front of number) out elements to suit. [ %145 146 147 %224 %440 440 ] def %-------------------------------------- %Things that don't have their own home /annot_color /green cvx def /worked_grid_square_color /verylightblue cvx def %-------------------------------------- %Rover and Mountain stuff /mountain_font_color /black cvx def /mountain_symbol_color /black cvx def /mountain_symbol_special_color /red cvx def /rover_font_color /lightblue cvx def /rover_symbol_color /lightblue cvx def % bearing distance lines to ROVER, MOUNTAIN etc % % some data types come in 2 flavors eg % rover:... % and % ROVER:... % % the lower case is plain vanilla, while the upper case is given % special attention. In the case of ROVER and MOUNTAIN, bearing % and distance information can be plotted as well as a line from % QTH to the ROVER or MOUNTAIN. However you don't have to plot % all three of these pieces of information. Here you can turn them % off one by one. /draw_distance_bearing_lines on def %on - line is drawn from QTH to ROVER or MOUNTAIN %off - lines is not drawn /show_bearing on def %on - bearing to ROVER or MOUNTAIN is put on the line %off - line is not labelled /show_distance on def %on - distance to ROVER or MOUNTAIN is put on the line %off - line is not labelled %-------------------------------------- %When to plot the grid squares %initialise saying that we haven't drawn the grid squares /grid_square_labels_on_paper off def %The order in which files are sent to the printer has some consequences %(see README.AZP) since objects are printed in the order generated by %the code. Hence objects printed later cover objects printed earlier. %Thus we recommend sending the grid.dat file (solid color) %for worked grid squares first, followed by the maps (.wdb files) %(lines and, if the lakes are filled, solid colors), followed by the text %and symbols (.dat files). %Somewhere in here the grid square borders and labels will be printed. %These are generated by the program and not from .dat files. %The program needs some way of determining when to print the grid square %borders. Since the program can't determine which files you may or may not %be going to send it, a mechanism for triggering the drawing of the %grid squares and labels is needed that doesn't depend on sending %any particular .dat or .wdb file. % %There are some asthetic concerns here as drawing the lat/lon lines %before the lakes, will show a lat/lon line going under a lake. %However if you draw the lat/lon lines after the map feature, the %state/country borders that are on major lat/lon lines will be %covered by the lat/lon lines. Whatever way you do it, something %will be in the wrong order. % %Here you get to choose when to draw the grid square labels and borders. %You can have grid square borders and labels, compass - %a)before the maps (but after the grid.dat file) %b)before the dat files (repeater, dxcc...) (but after the maps) %c)after all the input (.wdb, .dat) files have been processed (ie at the end). % %The program will print the grid squares and labels on the first %condition satisfied. Pick from the following. % %Any of these following choices will look OK if lake_fill is off. %If lake_fill is on, then choose false/true or false/false for %the next two variables. % /draw_grid_square_borders_and_labels_before_maps false def % true - draw on reading the first line of any map % (ie when first read .wdb formatted info) % (OK to be true if lake_fill off) % false - ignore map information in making decision to % draw grid square borders and labels /draw_grid_square_borders_and_labels_before_regular_dat_files true def % true - draw on before plotting any dat file except grid.dat % (OK to be true if lake_fill on) % false - ignore dat file information in deciding when to % draw grid square borders and labels %If both of these are false, the program will draw the grid square %borders and labels as it exits (ie after all the input files %have been processed). %-------------------------------------- /feature_color [ { black } % coast lines { black } % country borders { black } % Canadian Provinces { black } % US State boundaries { black } % islands { cyan } % lakes { green } % rivers { black } % Australian state boundaries ] def %-------------------------------------- /lake_fill on def % on/true - fill lakes with designated lake color % off/false - describe only outline of lakes, body of lake is white % if lake_fill on, color of lake edge % if lake_fill off, lake edge will be colored with feature_color for lake %/lake_edge_color {feature_color lake 1 sub get exec} def %same as lake /lake_edge_color {black} def %pick your own %-------------------------------------- % Execution is sloooow. % If you're calculating a map with ghostscript on a computer, you can % use these variables to reassure yourself that something is actually % happening and your computer has not locked up. % You can have these "on" if you have a launching window %(ie a window which is different to the window displaying the map) %to display these messages. You HAVE a lauching window in multitasking %systems like Windows, DesqViewX, X-window. You DO NOT have a lauching %window in MSDOS (where these messages will write all over your output) %or on a postscript printer (where the messages will come out on %subsequent pages). For these latter systems use "off". % /send_notices on def % stdout will get notifications of progess % On a computer, stdout is the screen. % On a postscript printer stdout goes to extra pages % following the wanted output. /verbose on def % output id of each path (small time penalty) % this is fine on a screen, when using ghostscript % but not useful on a real postscript printer, % where the notices may appear on subsequent % pages of error output. %-------------------------------------- userdict /#copies 1 put % a postscript command, number of copies to be printed. % the printer doesn't have to re-calculate everything, % & so subsequent pages are fast. %-------------------------------------- %--------------------------------------az_ini.ps